Skip to content

feat!: Remove BackgroundOperation and is_alive from UpdateProcessor - #557

Merged
keelerm84 merged 1 commit into
feat/10.xfrom
mk/SDK-2773/remove-background-operation
Nov 4, 2026
Merged

keelerm84 merged 1 commit into
feat/10.xfrom
mk/SDK-2773/remove-background-operation

Conversation

@keelerm84

@keelerm84 keelerm84 commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Summary

UpdateProcessor now declares start and stop itself and no longer inherits from BackgroundOperation, which is removed. Custom UpdateProcessor implementations no longer need to define is_alive, and code that imports BackgroundOperation must drop that import.


Note

Overview
This is a breaking public API change: the internal BackgroundOperation helper is deleted, and UpdateProcessor no longer inherits it. UpdateProcessor now defines start and stop directly (with updated docstrings) and no longer documents or requires is_alive.

Built-in no-op and test doubles are updated to match: NullUpdateProcessor, NullEventProcessor, and AsyncNullEventProcessor in stubs.py, plus MockUpdateProcessor, MockEventProcessor, and MockAsyncUpdateProcessor drop their is_alive implementations. Custom UpdateProcessor implementations and any code importing BackgroundOperation must be updated accordingly.

Reviewed by Cursor Bugbot for commit 1ed1fb8. Bugbot is set up for automated code reviews on this repo. Configure here.

UpdateProcessor now declares start and stop directly. Custom
UpdateProcessor implementations no longer need to define is_alive. Code
that referenced BackgroundOperation must drop that reference.
@keelerm84
keelerm84 requested a review from a team as a code owner November 2, 2026 20:17
@keelerm84
keelerm84 merged commit 7a5bdd6 into feat/10.x Nov 4, 2026
18 checks passed
@keelerm84
keelerm84 deleted the mk/SDK-2773/remove-background-operation branch November 4, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants